Understanding transition equivalence

Transition equivalence is the equality of a transition in one project definition workflow to a different transition in a different project definition workflow. This makes it possible to run a transition for one project in a batch of projects and have it run transitions in other projects within the batch even if the transitions don’t have the same name.

For example, consider a batch of three projects. The next and final transition of one of the projects is named Release and completes its workflow. The final transition of the other two projects is named Issue and completes their workflows. Also assume that a system administrator has defined the first project’s Release transition to be equivalent to the other projects’ Issue transition. By executing the first project’s Release transition, the other two projects’ Issue transitions will run as well, completing the workflows of all three projects in one step.

A system administrator can define transition equivalence between:

• All transitions to the same destination state
• All transitions with the same tag name
• All transitions from the same source state
• No other transition

Although very powerful, to end users may not understand transition equivalence right away. Explain, or better yet, document any transition equivalence for the end users.